Skip to content

Conversation

@crisbeto
Copy link
Member

The timepicker wasn't updating its internal state when it gets closed through the overlay which meant that the user can't reopen it.

Fixes #30558.

The timepicker wasn't updating its internal state when it gets closed through the overlay which meant that the user can't reopen it.

Fixes angular#30558.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Feb 27, 2025
@crisbeto crisbeto requested a review from a team as a code owner February 27, 2025 10:01
@crisbeto crisbeto requested review from mmalerba and wagnermaciel and removed request for a team February 27, 2025 10:01
@crisbeto crisbeto removed the request for review from mmalerba February 27, 2025 16:03
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Feb 27, 2025
@crisbeto crisbeto merged commit 9bc810c into angular:main Feb 27, 2025
22 of 25 checks passed
@crisbeto
Copy link
Member Author

The changes were merged into the following branches: main, 19.2.x

crisbeto added a commit that referenced this pull request Feb 27, 2025
…gy (#30561)

The timepicker wasn't updating its internal state when it gets closed through the overlay which meant that the user can't reopen it.

Fixes #30558.

(cherry picked from commit 9bc810c)
crisbeto added a commit to crisbeto/material2 that referenced this pull request Mar 6, 2025
angular#30561 accidentally switched the default scroll strategy for the timepicker to be `close` instead of `reposition`. It was unintentional so these changes switch it back to `reposition`.
crisbeto added a commit that referenced this pull request Mar 6, 2025
#30561 accidentally switched the default scroll strategy for the timepicker to be `close` instead of `reposition`. It was unintentional so these changes switch it back to `reposition`.
crisbeto added a commit that referenced this pull request Mar 6, 2025
#30561 accidentally switched the default scroll strategy for the timepicker to be `close` instead of `reposition`. It was unintentional so these changes switch it back to `reposition`.

(cherry picked from commit 3a97011)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 30, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: material/timepicker target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(Timepicker): Problem with MAT_TIMEPICKER_SCROLL_STRATEGY

2 participants